Rosetta Virtis emergency power off procedure

The aim of this Procedure is to describe the actions to be taken by the engineers with PL team approval, in case of instrument emergency triggered by OOLs/event

JUNO Jiram payload contingency plan

The aim of this document is to provide to the Juno project, the on-board configuration of JIRAM instrument, that should be loaded and then executed by the instrument, whenever it is necessary to verify the correct functioning of the instrument. This Payload Contingency Plan consists of two timelines, the first one to be used if the Spacecraft Dynamics are enabled, the second one if the Spacecraft Dynamics are not enabled

JUNO JIRAM radiation sequence architecture and instrument main miming characterization

The aim of this document is the definition of the JIRAM Radiation Sequence to be used in routine operation on Jupiter. The Radiation Sequence will allow an acquisition scheme where there is 120-degree relative spacing between three consecutive observations. Other customized pointings are also possible for the three consecutive observations. The absolute nadir offset values used for the three consecutive observations are flexible from sequence to sequence in order to allow coordination with the radiation measurements of other instruments. In order to properly configure the instrument to achieve the designed science goals and above all to validate the final sequence

JUNO Jiram uplink downlink procedures

The aim of the JIRAM Operation Procedures is to give flexibility to the JIRAM Science Community, in finalizing the science requests into instrument commands, and be able to process the data received from the instrument into the appropriate science data set within the time frame allocated in the Level-3 processes. In the uplink side, this involves being able to support the Science Planning Working Group (SPWG) in the planning of science activities, and being able to generate all the JIRAM commands that support the science plan. The downlink phase concentrates in being able to obtain/access the JIRAM instrument compressed level-2 science data from the File Exchange Interface (FEI) server, decompressing or expanding the data, calibrating the data (generating the level-3 science data), and producing the final higher-level science data products

JUNO Jiram operation procedure "Uplink"

The aim of the JIRAM Operation Procedures is to give flexibility to the JIRAM Science Community, in finalizing the science requests into instrument Tele-Commands and to give to the Operation Team the steps to follow for a correct implementation of Commanding products to be exchanged with the project

JUNO Jiram commanding tool software requirements

This document provides the basic requirements for the design and development of the JIRAM Ground Segment Commanding Tool. Additional requirements may be found in annexes (mainly details on the algorithms) and in the applicable and reference documents. The requirements specified here are subject to revision by GA when required. In the event that a supplier believes that parts of the specified requirements would not apply, or additional requirements are necessary, such recommendations shall be submitted to INAF with substantiating analyses and documentation, for consideration and analysis

JUNO Jiram planning commanding concepts

The purpose of this document is to describe and formalize Concepts and Rules to be satisfied in order to correctly operate the JIRAM instrument, during the interplanetary cruise phase and the Routine Operation Phase on Jupiter

JUNO Jiram operations - interface control document

The purpose of this document is to describe and formalize the structures and format of all the JIRAM commanding sequences, intended to be used for routine operations on Jupiter, at the earliest. The format proposed in this document is compatible with the JPL system architecture. However, in some few cases, fully described and highlighted with the blue colour, it is necessary a restyle of the JPL system’s configuration

JUNO JIRAM thermal consideration

The aim of this formal note is to clarify the behaviour of the JIRAM instrument, with the environment temperature, both in cruise and in routin

Marsis radar: Level 2 Processor Requirements

The primary task of Level 2 data processor is the Range Compression of the Marsis collected echoes during the subsurface modes (except for the SS2 Mode) and transmitted to the ground. These data are only compressed in azimuth on board (Doppler Filters output). Since these data have been distorted by the Ionosphere, we cannot use an ideal reference function (the ideal chirp) for range compression. Therefore we shall use the Contrast Method to estimate the Ionospheric distortion and to calculate a complex correction to modify the Ideal Reference Function in order to optimize the compressed signal